home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
QRZ! Ham Radio 4
/
QRZ Ham Radio Callsign Database - Volume 4.iso
/
digests
/
tcp
/
940171.txt
< prev
next >
Wrap
Internet Message Format
|
1994-11-13
|
6KB
Date: Fri, 12 Aug 94 04:30:01 PDT
From: Advanced Amateur Radio Networking Group <tcp-group@ucsd.edu>
Errors-To: TCP-Group-Errors@UCSD.Edu
Reply-To: TCP-Group@UCSD.Edu
Precedence: Bulk
Subject: TCP-Group Digest V94 #171
To: tcp-group-digest
TCP-Group Digest Fri, 12 Aug 94 Volume 94 : Issue 171
Today's Topics:
DNS (2 msgs)
FTP Multi-line mods
uploaded wnos-940812.zip
Send Replies or notes for publication to: <TCP-Group@UCSD.Edu>.
Subscription requests to <TCP-Group-REQUEST@UCSD.Edu>.
Problems you can't solve otherwise to brian@ucsd.edu.
Archives of past issues of the TCP-Group Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives".
We trust that readers are intelligent enough to realize that all text
herein consists of personal comments and does not represent the official
policies or positions of any party. Your mileage may vary. So there.
----------------------------------------------------------------------
Date: Thu, 11 Aug 1994 10:15:26 -0500 (CDT)
From: ssampson@sabea-oc.af.mil (Steve Sampson)
Subject: DNS
To: tcp-group@ucsd.edu
> ...NET source available on ftp.demon.co.uk
Alas, this machine is running an FTP with a MOTD which breaks
old FTP versions. FYI those little numbers in front of your MOTD
are a deviation from the spec.
--
Steve
------------------------------
Date: Thu, 11 Aug 94 15:40:46 GMT
From: "William Allen Simpson" <bill.simpson@um.cc.umich.edu>
Subject: DNS
To: crompton@nadc.nadc.navy.mil (D. Crompton)
I'm not on the nos-bbs list, only tcp-group and nos-hacks, so I'm
probably missing part of the debate.
> From: crompton@nadc.nadc.navy.mil (D. Crompton)
> I guess I don't understand. I use JNOS as a client
> server DNS on my gateway and it works fine. The
> ham community uses the gateway (JNOS) address as
> their server and that machine is in turn a client
> to a server on the internet.
>
Since I don't use JNOS, I'm unaware of its capabilities. I'm happy to learn
that someone has worked on server capability. If there's a big demand, I'm
sure other NOS variants will include it.
> I have done a couple of things that stop potential
> problems. I want this machine to really just act
> as a domain "repeater". Therefore I have no local
> domain file, nor do I do local domain updates. I
> also have the cache size set low (4 as I remember)
> and I made a few changes to the code that have been
> in the 108dxx stuff for awhile.
>
Eventually, my plan is to do resource discovery (another IETF WG), and
then everyone can automatically find where the DNS servers are. No need
for configuration or repeaters.
Until then, this sounds like a good idea.
Bill.Simpson@um.cc.umich.edu
------------------------------
Date: Thu, 11 Aug 1994 11:18:27 -0500 (CDT)
From: ssampson@sabea-oc.af.mil (Steve Sampson)
Subject: FTP Multi-line mods
To: tcp-group@ucsd.edu
In ftpserv.c maybe this will suffice:
static void
sendmsgfile(int s,int num,char *buf,int size,FILE *fp)
{
while(fgets(buf,size,fp)) {
rip(buf);
usprintf(s," %d- %s\n",num,buf);
}
}
and:
static void
ftpserv(s,unused,p)
int s; /* Socket with user connection */
void *unused;
void *p;
{
...
/* now go say 'hello' */
usprintf(s,banner,Hostname,Version);
if((fp = fopen(Ftpmotd,"r")) != NULL) {
while(fgets(buf,128,fp)) {
rip(buf);
usprintf(s," 220- %s\n",buf);
}
fclose(fp);
}
...
}
In ftpcli.c maybe this will suffice:
/* Wait for, read and display response from FTP server. Return the result code.
*/
static int
getresp(ftp,mincode)
struct ftpcli *ftp;
int mincode; /* Keep reading until at least this code comes back */
{
...
/* Messages with dashes are continued */
>>>>>>> if(line[5] != '-' && rval >= mincode) <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
break;
...
}
I'm assuming the atoi() in getresp will still work with padded numbers.
----
RFC959 discusses multi-line responses this way:
Thus the format for multi-line replies is that the first line
will begin with the exact required reply code, followed
immediately by a Hyphen, "-" (also known as Minus), followed by
text. The last line will begin with the same code, followed
immediately by Space <SP>, optionally some text, and the Telnet
end-of-line code.
For example:
123-First line
Second line
[NOTICE THE SPACES] 234 A line beginning with numbers
123 The last line
The user-process then simply needs to search for the second
occurrence of the same reply code, followed by <SP> (Space), at
the beginning of a line, and ignore all intermediary lines.
>>>> If an intermediary line begins with a 3-digit number, the <<<<
>>>> Server must pad the front to avoid confusion. <<<<
We covered this before on the group, but the JNOS files and its derivatives
haven't been fixed yet.
--
Steve
------------------------------
Date: Fri, 12 Aug 94 09:10:29 EST
From: BARRY TITMARSH <BTITMARS%ESOC.BITNET@vm.gmd.de>
Subject: uploaded wnos-940812.zip
To: TCP-GROUP <TCP-GROUP@ucsd.edu>
Ok i have just uploaded to ftp.ucsd.edu:/.../incoming/wnos-940812.zip
this has some more bugs fixed, and i have ported from other versions
crc smack for kiss, rlogin, a new ax25 heard list with type of traffic
detection (thanks to g6dhu, mike ;-) )
improved ftp server for use with UNIX, Improved nntp client/server
thanks to dg1zx etc..
as before it compiles with out problem on BC++ 2.00 not tested
on any other compiler. Use at your risc.
test it, hack it, discard it. what ever you wish.
Enjoy Barry.
PS. Next on the list is dama_slave.
------------------------------
End of TCP-Group Digest V94 #171
******************************